Hello, We have experienced a BSOD on Windows Server 2008 .We have also checked & found that there is No Hardware Issue on that Server by Observing the Logs .Kindly help on this Issue as early as possible. Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6002.2.2.0.16.7 Locale ID: 1033 Additional information about the problem: BCCode: d1 BCP1: 0000000000000000 BCP2: 0000000000000002 BCP3: 0000000000000001 BCP4: FFFFFA6005BCE547 OS Version: 6_0_6002 Service Pack: 2_0 Product: 16_3 Files that help describe the problem: C:\Windows\Minidump\Mini012411-01.dmp C:\Users\administrator.SCI\AppData\Local\Temp\1\WER-232160-0.sysdata.xml C:\Users\administrator.SCI\AppData\Local\Temp\1\WERC782.tmp.version.txt Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409 Regards, Satam AmitDeva Self-trust is the first secret of success.

A bugcheck (BSOD) is a mechanism to protect your PC from damage. Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL . This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. http://msdn.microsoft.com/en-us/library/ff560244%28VS.85%29.aspx To see the causing driver I have to take a look at the dumps with the Debugging Tools for Windows. Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

You may boot in Clean Boot Mode. Perform a clean startup to determine whether background programs are interfering with your game or program If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause. Another way is enable muni-dump and use Windbg. Please refer: How to read the small memory dump files that Windows creates for debugging You may paste the result in your next post for analyzing. Additionally, since your system is Windows Server 2008, it is better to discuss in our Windows Server forum.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.